Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Only display last error when failing after multiple retries #200

Merged
merged 1 commit into from
Sep 7, 2021
Merged

Only display last error when failing after multiple retries #200

merged 1 commit into from
Sep 7, 2021

Conversation

kke
Copy link
Contributor

@kke kke commented Sep 7, 2021

When logs like these are pasted to github (outside of a backticked code block):

#97: failed to parse status from kubectl output
#98: failed to parse status from kubectl output
#99: failed to parse status from kubectl output
#100: failed to parse status from kubectl output
#101: failed to parse status from kubectl output
#102: failed to parse status from kubectl output
#103: failed to parse status from kubectl output
#104: failed to parse status from kubectl output

You get a load of references to issues and PR's ("xxx mentioned this PR in issue # 97").

Also it's a lot easier on the eyes.

@kke kke added the enhancement New feature or request label Sep 7, 2021
@kke kke merged commit d5275fd into main Sep 7, 2021
@kke kke deleted the retry-messages branch September 7, 2021 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@kke